Measurement model based on uplink signals with reciprocity to downlink beam

ABSTRACT

In an aspect, a network component (e.g., BS, server, etc.) obtains measurement information associated with uplink signal(s) from UE(s), with the uplink signal(s) having reciprocity with one or more downlink beams of wireless node(s) (e.g., TRP, reference UE, etc.). The network component determines (e.g., generates or refines) a meausrement (e.g., RFFP-P) model based on the measurement information. The network component provides the measurement (e.g., RFFP-P) model to a target UE. The target UE receives at least one signal (e.g., PRS) on the one or more downlink beams from the wireless node(s). The target UE processes the at least one signal (e.g., predicts target UE location) based at least in part on the measurement (e.g., RFFP-P) model.

BACKGROUND OF THE DISCLOSURE 1. Field of the Disclosure

Aspects of the disclosure relate generally to wireless communications.

2. Description of the Related Art

Wireless communication systems have developed through various generations, including a first-generation analog wireless phone service (1G), a second-generation (2G) digital wireless phone service (including interim 2.5G and 2.75G networks), a third-generation (3G) high speed data, Internet-capable wireless service and a fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). There are presently many different types of wireless communication systems in use, including cellular and personal communications service (PCS) systems. Examples of known cellular systems include the cellular analog advanced mobile phone system (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), the Global System for Mobile communications (GSM), etc.

A fifth generation (5G) wireless standard, referred to as New Radio (NR), calls for higher data transfer speeds, greater numbers of connections, and better coverage, among other improvements. The 5G standard, according to the Next Generation Mobile Networks Alliance, is designed to provide data rates of several tens of megabits per second to each of tens of thousands of users, with 1 gigabit per second to tens of workers on an office floor. Several hundreds of thousands of simultaneous connections should be supported in order to support large sensor deployments. Consequently, the spectral efficiency of 5G mobile communications should be significantly enhanced compared to the current 4G standard. Furthermore, signaling efficiencies should be enhanced and latency should be substantially reduced compared to current standards.

SUMMARY

The following presents a simplified summary relating to one or more aspects disclosed herein. Thus, the following summary should not be considered an extensive overview relating to all contemplated aspects, nor should the following summary be considered to identify key or critical elements relating to all contemplated aspects or to delineate the scope associated with any particular aspect. Accordingly, the following summary has the sole purpose to present certain concepts relating to one or more aspects relating to the mechanisms disclosed herein in a simplified form to precede the detailed description presented below.

In an aspect, a method of operating a network component includes obtaining measurement information associated with a set of uplink signals from one or more user equipments (UEs), wherein the set of uplink signals has reciprocity with one or more downlink beams of one or more wireless nodes; determining a measurement model based on the measurement information associated with the set of uplink signals from the one or more UEs; and providing, to a target UE, the measurement model for processing of at least one signal associated with the one or more downlink beams of the one or more wireless nodes.

In an aspect, a method of operating a target user equipment (UE) includes receiving, from a network component, a measurement model that is trained based upon measurement information associated with a set of uplink signals from one or more UEs, the set of uplink signals having reciprocity with one or more downlink beams of one or more wireless nodes; receiving, on the one or more downlink beams from the one or more wireless nodes, at least one signal; and processing the at least one signal based at least in part on the measurement model.

In an aspect, a network component includes a memory; a communication interface; and at least one processor communicatively coupled to the memory and the communication interface, the at least one processor configured to: obtain measurement information associated with a set of uplink signals from one or more user equipments (UEs), wherein the set of uplink signals has reciprocity with one or more downlink beams of one or more wireless nodes; determine a measurement model based on the measurement information associated with the set of uplink signals from the one or more UEs; and provide, to a target UE, the measurement model for processing of at least one signal associated with the one or more downlink beams of the one or more wireless nodes.

In an aspect, a target user equipment (UE) includes a memory; a communication interface; and at least one processor communicatively coupled to the memory and the communication interface, the at least one processor configured to: receive, via the communication interface, from a network component, a measurement model that is trained based upon measurement information associated with a set of uplink signals from one or more UEs, the set of uplink signals having reciprocity with one or more downlink beams of one or more wireless nodes; receive, via the communication interface, on the one or more downlink beams from the one or more wireless nodes, at least one signal; and process the at least one signal based at least in part on the measurement model. Other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are presented to aid in the description of various aspects of the disclosure and are provided solely for illustration of the aspects and not limitation thereof.

FIG. 1 illustrates an example wireless communications system, according to aspects of the disclosure.

FIGS. 2A and 2B illustrate example wireless network structures, according to aspects of the disclosure.

FIGS. 3A to 3C are simplified block diagrams of several sample aspects of components that may be employed in a user equipment (UE), a base station, and a network entity, respectively, and configured to support communications as taught herein.

FIGS. 4A to 4D are diagrams illustrating example frame structures and channels within the frame structures, according to aspects of the disclosure.

FIG. 5 illustrates a neural network (NN) in accordance with an aspect of the disclosure.

FIG. 6 illustrates an example of an RFFP-P model process in accordance with an aspect of the disclosure.

FIG. 7 is a diagram illustrating an example base station in communication with an example UE, according to aspects of the disclosure.

FIG. 8 illustrates an exemplary process of wireless communication, according to aspects of the disclosure.

FIG. 9 illustrates an exemplary process of wireless communication, according to aspects of the disclosure.

FIG. 10 illustrates an example implementation of the processes of FIGS. 8-9 in accordance with an aspect of the disclosure.

FIG. 11 illustrates an example implementation of the processes of FIGS. 8-9 in accordance with another aspect of the disclosure.

FIG. 12 illustrates an example implementation of the processes of FIGS. 8-9 in accordance with another aspect of the disclosure.

DETAILED DESCRIPTION

Aspects of the disclosure are provided in the following description and related drawings directed to various examples provided for illustration purposes. Alternate aspects may be devised without departing from the scope of the disclosure. Additionally, well-known elements of the disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of the disclosure.

The words “exemplary” and/or “example” are used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” and/or “example” is not necessarily to be construed as preferred or advantageous over other aspects. Likewise, the term “aspects of the disclosure” does not require that all aspects of the disclosure include the discussed feature, advantage or mode of operation.

Those of skill in the art will appreciate that the information and signals described below may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description below may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof, depending in part on the particular application, in part on the desired design, in part on the corresponding technology, etc.

Further, many aspects are described in terms of sequences of actions to be performed by, for example, elements of a computing device. It will be recognized that various actions described herein can be performed by specific circuits (e.g., application specific integrated circuits (ASICs)), by program instructions being executed by one or more processors, or by a combination of both. Additionally, the sequence(s) of actions described herein can be considered to be embodied entirely within any form of non-transitory computer-readable storage medium having stored therein a corresponding set of computer instructions that, upon execution, would cause or instruct an associated processor of a device to perform the functionality described herein. Thus, the various aspects of the disclosure may be embodied in a number of different forms, all of which have been contemplated to be within the scope of the claimed subject matter. In addition, for each of the aspects described herein, the corresponding form of any such aspects may be described herein as, for example, “logic configured to” perform the described action.

As used herein, the terms “user equipment” (UE) and “base station” are not intended to be specific or otherwise limited to any particular radio access technology (RAT), unless otherwise noted. In general, a UE may be any wireless communication device (e.g., a mobile phone, router, tablet computer, laptop computer, consumer asset locating device, wearable (e.g., smartwatch, glasses, augmented reality (AR)/virtual reality (VR) headset, etc.), vehicle (e.g., automobile, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communications network. A UE may be mobile or may (e.g., at certain times) be stationary, and may communicate with a radio access network (RAN). As used herein, the term “UE” may be referred to interchangeably as an “access terminal” or “AT,” a “client device,” a “wireless device,” a “subscriber device,” a “subscriber terminal,” a “subscriber station,” a “user terminal” or “UT,” a “mobile device,” a “mobile terminal,” a “mobile station,” or variations thereof. Generally, UEs can communicate with a core network via a RAN, and through the core network the UEs can be connected with external networks such as the Internet and with other UEs. Of course, other mechanisms of connecting to the core network and/or the Internet are also possible for the UEs, such as over wired access networks, wireless local area network (WLAN) networks (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.) and so on.

A base station may operate according to one of several RATs in communication with UEs depending on the network in which it is deployed, and may be alternatively referred to as an access point (AP), a network node, a NodeB, an evolved NodeB (eNB), a next generation eNB (ng-eNB), a New Radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A base station may be used primarily to support wireless access by UEs, including supporting data, voice, and/or signaling connections for the supported UEs. In some systems a base station may provide purely edge node signaling functions while in other systems it may provide additional control and/or network management functions. A communication link through which UEs can send signals to a base station is called an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). A communication link through which the base station can send signals to UEs is called a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein the term traffic channel (TCH) can refer to either an uplink/reverse or downlink/forward traffic channel.

The term “base station” may refer to a single physical transmission-reception point (TRP) or to multiple physical TRPs that may or may not be co-located. For example, where the term “base station” refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to a cell (or several cell sectors) of the base station. Where the term “base station” refers to multiple co-located physical TRPs, the physical TRPs may be an array of antennas (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming) of the base station. Where the term “base station” refers to multiple non-co-located physical TRPs, the physical TRPs may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRPs may be the serving base station receiving the measurement report from the UE and a neighbor base station whose reference radio frequency (RF) signals the UE is measuring. Because a TRP is the point from which a base station transmits and receives wireless signals, as used herein, references to transmission from or reception at a base station are to be understood as referring to a particular TRP of the base station.

In some implementations that support positioning of UEs, a base station may not support wireless access by UEs (e.g., may not support data, voice, and/or signaling connections for UEs), but may instead transmit reference signals to UEs to be measured by the UEs, and/or may receive and measure signals transmitted by the UEs. Such a base station may be referred to as a positioning beacon (e.g., when transmitting signals to UEs) and/or as a location measurement unit (e.g., when receiving and measuring signals from UEs).

An “RF signal” comprises an electromagnetic wave of a given frequency that transports information through the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single “RF signal” or multiple “RF signals” to a receiver. However, the receiver may receive multiple “RF signals” corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through multipath channels. The same transmitted RF signal on different paths between the transmitter and receiver may be referred to as a “multipath” RF signal.

FIG. 1 illustrates an example wireless communications system 100, according to aspects of the disclosure. The wireless communications system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled “BS”) and various UEs 104. The base stations 102 may include macro cell base stations (high power cellular base stations) and/or small cell base stations (low power cellular base stations). In an aspect, the macro cell base station may include eNBs and/or ng-eNBs where the wireless communications system 100 corresponds to an LTE network, or gNBs where the wireless communications system 100 corresponds to a NR network, or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.

The base stations 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) through backhaul links 122, and through the core network 170 to one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)). The location server(s) 172 may be part of core network 170 or may be external to core network 170. In addition to other functions, the base stations 102 may perform functions that relate to one or more of transferring user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC/5GC) over backhaul links 134, which may be wired or wireless.

The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. In an aspect, one or more cells may be supported by a base station 102 in each geographic coverage area 110. A “cell” is a logical communication entity used for communication with a base station (e.g., over some frequency resource, referred to as a carrier frequency, component carrier, carrier, band, or the like), and may be associated with an identifier (e.g., a physical cell identifier (PCI), a virtual cell identifier (VCI), a cell global identifier (CGI)) for distinguishing cells operating via the same or a different carrier frequency. In some cases, different cells may be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of UEs. Because a cell is supported by a specific base station, the term “cell” may refer to either or both of the logical communication entity and the base station that supports it, depending on the context. In some cases, the term “cell” may also refer to a geographic coverage area of a base station (e.g., a sector), insofar as a carrier frequency can be detected and used for communication within some portion of geographic coverage areas 110.

While neighboring macro cell base station 102 geographic coverage areas 110 may partially overlap (e.g., in a handover region), some of the geographic coverage areas 110 may be substantially overlapped by a larger geographic coverage area 110. For example, a small cell (SC) base station 102′ may have a geographic coverage area 110′ that substantially overlaps with the geographic coverage area 110 of one or more macro cell base stations 102. A network that includes both small cell and macro cell base stations may be known as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG).

The communication links 120 between the base stations 102 and the UEs 104 may include uplink (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links 120 may be through one or more carrier frequencies. Allocation of carriers may be asymmetric with respect to downlink and uplink (e.g., more or less carriers may be allocated for downlink than for uplink).

The wireless communications system 100 may further include a wireless local area network (WLAN) access point (AP) 150 in communication with WLAN stations (STAs) 152 via communication links 154 in an unlicensed frequency spectrum (e.g., 5 GHz). When communicating in an unlicensed frequency spectrum, the WLAN STAs 152 and/or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure prior to communicating in order to determine whether the channel is available.

The small cell base station 102′ may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell base station 102′ may employ LTE or NR technology and use the same 5 GHz unlicensed frequency spectrum as used by the WLAN AP 150. The small cell base station 102′, employing LTE/5G in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network. NR in unlicensed spectrum may be referred to as NR-U. LTE in an unlicensed spectrum may be referred to as LTE-U, licensed assisted access (LAA), or MulteFire.

The wireless communications system 100 may further include a millimeter wave (mmW) base station 180 that may operate in mmW frequencies and/or near mmW frequencies in communication with a UE 182. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in this band may be referred to as a millimeter wave. Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW/near mmW radio frequency band have high path loss and a relatively short range. The mmW base station 180 and the UE 182 may utilize beamforming (transmit and/or receive) over a mmW communication link 184 to compensate for the extremely high path loss and short range. Further, it will be appreciated that in alternative configurations, one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Accordingly, it will be appreciated that the foregoing illustrations are merely examples and should not be construed to limit the various aspects disclosed herein.

Transmit beamforming is a technique for focusing an RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omni-directionally). With transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal for the receiving device(s). To change the directionality of the RF signal when transmitting, a network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that are broadcasting the RF signal. For example, a network node may use an array of antennas (referred to as a “phased array” or an “antenna array”) that creates a beam of RF waves that can be “steered” to point in different directions, without actually moving the antennas. Specifically, the RF current from the transmitter is fed to the individual antennas with the correct phase relationship so that the radio waves from the separate antennas add together to increase the radiation in a desired direction, while cancelling to suppress radiation in undesired directions.

Transmit beams may be quasi-co-located, meaning that they appear to the receiver (e.g., a UE) as having the same parameters, regardless of whether or not the transmitting antennas of the network node themselves are physically co-located. In NR, there are four types of quasi-co-location (QCL) relations. Specifically, a QCL relation of a given type means that certain parameters about a target reference RF signal on a target beam can be derived from information about a source reference RF signal on a source beam. If the source reference RF signal is QCL Type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of a target reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of a target reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of a target reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type D, the receiver can use the source reference RF signal to estimate the spatial receive parameter of a target reference RF signal transmitted on the same channel.

In receive beamforming, the receiver uses a receive beam to amplify RF signals detected on a given channel. For example, the receiver can increase the gain setting and/or adjust the phase setting of an array of antennas in a particular direction to amplify (e.g., to increase the gain level of) the RF signals received from that direction. Thus, when a receiver is said to beamform in a certain direction, it means the beam gain in that direction is high relative to the beam gain along other directions, or the beam gain in that direction is the highest compared to the beam gain in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR), etc.) of the RF signals received from that direction.

Receive beams may be spatially related. A spatial relation means that parameters for a transmit beam for a second reference signal can be derived from information about a receive beam for a first reference signal. For example, a UE may use a particular receive beam to receive one or more reference downlink reference signals (e.g., positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signal (PTRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), primary synchronization signals (PSS), secondary synchronization signals (SSS), synchronization signal blocks (SSBs), etc.) from a base station. The UE can then form a transmit beam for sending one or more uplink reference signals (e.g., uplink positioning reference signals (UL-PRS), sounding reference signal (SRS), demodulation reference signals (DMRS), PTRS, etc.) to that base station based on the parameters of the receive beam.

Note that a “downlink” beam may be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming the downlink beam to transmit a reference signal to a UE, the downlink beam is a transmit beam. If the UE is forming the downlink beam, however, it is a receive beam to receive the downlink reference signal. Similarly, an “uplink” beam may be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming the uplink beam, it is an uplink receive beam, and if a UE is forming the uplink beam, it is an uplink transmit beam.

In 5G, the frequency spectrum in which wireless nodes (e.g., base stations 102/180, UEs 104/182) operate is divided into multiple frequency ranges, FR1 (from 450 to 6000 MHz), FR2 (from 24250 to 52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). In a multi-carrier system, such as 5G, one of the carrier frequencies is referred to as the “primary carrier” or “anchor carrier” or “primary serving cell” or “PCell,” and the remaining carrier frequencies are referred to as “secondary carriers” or “secondary serving cells” or “SCells.” In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by a UE 104/182 and the cell in which the UE 104/182 either performs the initial radio resource control (RRC) connection establishment procedure or initiates the RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels, and may be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured once the RRC connection is established between the UE 104 and the anchor carrier and that may be used to provide additional radio resources. In some cases, the secondary carrier may be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals, for example, those that are UE-specific may not be present in the secondary carrier, since both primary uplink and downlink carriers are typically UE-specific. This means that different UEs 104/182 in a cell may have different downlink primary carriers. The same is true for the uplink primary carriers. The network is able to change the primary carrier of any UE 104/182 at any time. This is done, for example, to balance the load on different carriers. Because a “serving cell” (whether a PCell or an SCell) corresponds to a carrier frequency/component carrier over which some base station is communicating, the term “cell,” “serving cell,” “component carrier,” “carrier frequency,” and the like can be used interchangeably.

For example, still referring to FIG. 1, one of the frequencies utilized by the macro cell base stations 102 may be an anchor carrier (or “PCell”) and other frequencies utilized by the macro cell base stations 102 and/or the mmW base station 180 may be secondary carriers (“SCells”). The simultaneous transmission and/or reception of multiple carriers enables the UE 104/182 to significantly increase its data transmission and/or reception rates. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically lead to a two-fold increase in data rate (i.e., 40 MHz), compared to that attained by a single 20 MHz carrier.

The wireless communications system 100 may further include a UE 164 that may communicate with a macro cell base station 102 over a communication link 120 and/or the mmW base station 180 over a mmW communication link 184. For example, the macro cell base station 102 may support a PCell and one or more SCells for the UE 164 and the mmW base station 180 may support one or more SCells for the UE 164.

In the example of FIG. 1, one or more Earth orbiting satellite positioning system (SPS) space vehicles (SVs) 112 (e.g., satellites) may be used as an independent source of location information for any of the illustrated UEs (shown in FIG. 1 as a single UE 104 for simplicity). A UE 104 may include one or more dedicated SPS receivers specifically designed to receive SPS signals 124 for deriving geo location information from the SVs 112. An SPS typically includes a system of transmitters (e.g., SVs 112) positioned to enable receivers (e.g., UEs 104) to determine their location on or above the Earth based, at least in part, on signals (e.g., SPS signals 124) received from the transmitters. Such a transmitter typically transmits a signal marked with a repeating pseudo-random noise (PN) code of a set number of chips. While typically located in SVs 112, transmitters may sometimes be located on ground-based control stations, base stations 102, and/or other UEs 104.

The use of SPS signals 124 can be augmented by various satellite-based augmentation systems (SBAS) that may be associated with or otherwise enabled for use with one or more global and/or regional navigation satellite systems. For example an SBAS may include an augmentation system(s) that provides integrity information, differential corrections, etc., such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multi-functional Satellite Augmentation System (MSAS), the Global Positioning System (GPS) Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system (GAGAN), and/or the like. Thus, as used herein, an SPS may include any combination of one or more global and/or regional navigation satellite systems and/or augmentation systems, and SPS signals 124 may include SPS, SPS-like, and/or other signals associated with such one or more SPS.

The wireless communications system 100 may further include one or more UEs, such as UE 190, that connects indirectly to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “sidelinks”). In the example of FIG. 1, UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., through which UE 190 may indirectly obtain cellular connectivity) and a D2D P2P link 194 with WLAN STA 152 connected to the WLAN AP 150 (through which UE 190 may indirectly obtain WLAN-based Internet connectivity). In an example, the D2D P2P links 192 and 194 may be supported with any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth®, and so on.

FIG. 2A illustrates an example wireless network structure 200. For example, a 5GC 210 (also referred to as a Next Generation Core (NGC)) can be viewed functionally as control plane functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane functions 212, (e.g., UE gateway function, access to data networks, IP routing, etc.) which operate cooperatively to form the core network. User plane interface (NG-U) 213 and control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210 and specifically to the control plane functions 214 and user plane functions 212. In an additional configuration, an ng-eNB 224 may also be connected to the 5GC 210 via NG-C 215 to the control plane functions 214 and NG-U 213 to user plane functions 212. Further, ng-eNB 224 may directly communicate with gNB 222 via a backhaul connection 223. In some configurations, a Next Generation RAN (NG-RAN) 220 may only have one or more gNBs 222, while other configurations include one or more of both ng-eNBs 224 and gNBs 222. Either gNB 222 or ng-eNB 224 may communicate with UEs 204 (e.g., any of the UEs depicted in FIG. 1). Another optional aspect may include location server 230, which may be in communication with the 5GC 210 to provide location assistance for UEs 204. The location server 230 can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server. The location server 230 can be configured to support one or more location services for UEs 204 that can connect to the location server 230 via the core network, 5GC 210, and/or via the Internet (not illustrated). Further, the location server 230 may be integrated into a component of the core network, or alternatively may be external to the core network (e.g., a third party server, such as an original equipment manufacturer (OEM) server or service server).

FIG. 2B illustrates another example wireless network structure 250. A 5GC 260 (which may correspond to 5GC 210 in FIG. 2A) can be viewed functionally as control plane functions, provided by an access and mobility management function (AMF) 264, and user plane functions, provided by a user plane function (UPF) 262, which operate cooperatively to form the core network (i.e., 5GC 260). User plane interface 263 and control plane interface 265 connect the ng-eNB 224 to the 5GC 260 and specifically to UPF 262 and AMF 264, respectively. In an additional configuration, a gNB 222 may also be connected to the 5GC 260 via control plane interface 265 to AMF 264 and user plane interface 263 to UPF 262. Further, ng-eNB 224 may directly communicate with gNB 222 via the backhaul connection 223, with or without gNB direct connectivity to the 5GC 260. In some configurations, the NG-RAN 220 may only have one or more gNBs 222, while other configurations include one or more of both ng-eNBs 224 and gNBs 222. Either gNB 222 or ng-eNB 224 may communicate with UEs 204 (e.g., any of the UEs depicted in FIG. 1). The base stations of the NG-RAN 220 communicate with the AMF 264 over the N2 interface and with the UPF 262 over the N3 interface.

The functions of the AMF 264 include registration management, connection management, reachability management, mobility management, lawful interception, transport for session management (SM) messages between the UE 204 and a session management function (SMF) 266, transparent proxy services for routing SM messages, access authentication and access authorization, transport for short message service (SMS) messages between the UE 204 and the short message service function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF 264 also interacts with an authentication server function (AUSF) (not shown) and the UE 204, and receives the intermediate key that was established as a result of the UE 204 authentication process. In the case of authentication based on a UMTS (universal mobile telecommunications system) subscriber identity module (USIM), the AMF 264 retrieves the security material from the AUSF. The functions of the AMF 264 also include security context management (SCM). The SCM receives a key from the SEAF that it uses to derive access-network specific keys. The functionality of the AMF 264 also includes location services management for regulatory services, transport for location services messages between the UE 204 and an LMF 270 (which acts as a location server 230), transport for location services messages between the NG-RAN 220 and the LMF 270, evolved packet system (EPS) bearer identifier allocation for interworking with the EPS, and UE 204 mobility event notification. In addition, the AMF 264 also supports functionalities for non-3GPP (Third Generation Partnership Project) access networks.

Functions of the UPF 262 include acting as an anchor point for intra-/inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point of interconnect to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) handling for the user plane (e.g., uplink/downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic verification (service data flow (SDF) to QoS flow mapping), transport level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and sending and forwarding of one or more “end markers” to the source RAN node. The UPF 262 may also support transfer of location services messages over a user plane between the UE 204 and a location server, such as an SLP 272.

The functions of the SMF 266 include session management, UE Internet protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering at the UPF 262 to route traffic to the proper destination, control of part of policy enforcement and QoS, and downlink data notification. The interface over which the SMF 266 communicates with the AMF 264 is referred to as the N11 interface.

Another optional aspect may include an LMF 270, which may be in communication with the 5GC 260 to provide location assistance for UEs 204. The LMF 270 can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server. The LMF 270 can be configured to support one or more location services for UEs 204 that can connect to the LMF 270 via the core network, 5GC 260, and/or via the Internet (not illustrated). The SLP 272 may support similar functions to the LMF 270, but whereas the LMF 270 may communicate with the AMF 264, NG-RAN 220, and UEs 204 over a control plane (e.g., using interfaces and protocols intended to convey signaling messages and not voice or data), the SLP 272 may communicate with UEs 204 and external clients (not shown in FIG. 2B) over a user plane (e.g., using protocols intended to carry voice and/or data like the transmission control protocol (TCP) and/or IP).

FIGS. 3A, 3B, and 3C illustrate several example components (represented by corresponding blocks) that may be incorporated into a UE 302 (which may correspond to any of the UEs described herein), a base station 304 (which may correspond to any of the base stations described herein), and a network entity 306 (which may correspond to or embody any of the network functions described herein, including the location server 230 and the LMF 270, to alternatively may be independent from the cellular RAN or 5GC infrastructure depicted in FIGS. 2A-2B, such as a private network) to support the file transmission operations as taught herein. It will be appreciated that these components may be implemented in different types of apparatuses in different implementations (e.g., in an ASIC, in a system-on-chip (SoC), etc.). The illustrated components may also be incorporated into other apparatuses in a communication system. For example, other apparatuses in a system may include components similar to those described to provide similar functionality. Also, a given apparatus may contain one or more of the components. For example, an apparatus may include multiple transceiver components that enable the apparatus to operate on multiple carriers and/or communicate via different technologies.

The UE 302 and the base station 304 each include wireless wide area network (WWAN) transceiver 310 and 350, respectively, providing means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, etc.) via one or more wireless communication networks (not shown), such as an NR network, an LTE network, a GSM network, and/or the like. The WWAN transceivers 310 and 350 may be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes, such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc., via at least one designated RAT (e.g., NR, LTE, GSM, etc.) over a wireless communication medium of interest (e.g., some set of time/frequency resources in a particular frequency spectrum). The WWAN transceivers 310 and 350 may be variously configured for transmitting and encoding signals 318 and 358 (e.g., messages, indications, information, and so on), respectively, and, conversely, for receiving and decoding signals 318 and 358 (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT. Specifically, the WWAN transceivers 310 and 350 include one or more transmitters 314 and 354, respectively, for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352, respectively, for receiving and decoding signals 318 and 358, respectively.

The UE 302 and the base station 304 also include, at least in some cases, one or more short-range wireless transceivers 320 and 360, respectively. The short-range wireless transceivers 320 and 360 may be connected to one or more antennas 326 and 366, respectively, and provide means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, etc.) with other network nodes, such as other UEs, access points, base stations, etc., via at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth®, Zigbee®, Z-Wave®, PC5, dedicated short-range communications (DSRC), wireless access for vehicular environments (WAVE), near-field communication (NFC), etc.) over a wireless communication medium of interest. The short-range wireless transceivers 320 and 360 may be variously configured for transmitting and encoding signals 328 and 368 (e.g., messages, indications, information, and so on), respectively, and, conversely, for receiving and decoding signals 328 and 368 (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT. Specifically, the short-range wireless transceivers 320 and 360 include one or more transmitters 324 and 364, respectively, for transmitting and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362, respectively, for receiving and decoding signals 328 and 368, respectively. As specific examples, the short-range wireless transceivers 320 and 360 may be WiFi transceivers, Bluetooth® transceivers, Zigbee® and/or Z-Wave® transceivers, NFC transceivers, or vehicle-to-vehicle (V2V) and/or vehicle-to-everything (V2X) transceivers.

Transceiver circuitry including at least one transmitter and at least one receiver may comprise an integrated device (e.g., embodied as a transmitter circuit and a receiver circuit of a single communication device) in some implementations, may comprise a separate transmitter device and a separate receiver device in some implementations, or may be embodied in other ways in other implementations. In an aspect, a transmitter may include or be coupled to a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, that permits the respective apparatus to perform transmit “beamforming,” as described herein. Similarly, a receiver may include or be coupled to a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, that permits the respective apparatus to perform receive beamforming, as described herein. In an aspect, the transmitter and receiver may share the same plurality of antennas (e.g., antennas 316, 326, 356, 366), such that the respective apparatus can only receive or transmit at a given time, not both at the same time. A wireless communication device (e.g., one or both of the transceivers 310 and 320 and/or 350 and 360) of the UE 302 and/or the base station 304 may also comprise a network listen module (NLM) or the like for performing various measurements.

The UE 302 and the base station 304 also include, at least in some cases, satellite positioning systems (SPS) receivers 330 and 370. The SPS receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may provide means for receiving and/or measuring SPS signals 338 and 378, respectively, such as global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. The SPS receivers 330 and 370 may comprise any suitable hardware and/or software for receiving and processing SPS signals 338 and 378, respectively. The SPS receivers 330 and 370 request information and operations as appropriate from the other systems, and performs calculations necessary to determine positions of the UE 302 and the base station 304 using measurements obtained by any suitable SPS algorithm.

The base station 304 and the network entity 306 each include at least one network interfaces 380 and 390, respectively, providing means for communicating (e.g., means for transmitting, means for receiving, etc.) with other network entities. For example, the network interfaces 380 and 390 (e.g., one or more network access ports) may be configured to communicate with one or more network entities via a wire-based or wireless backhaul connection. In some aspects, the network interfaces 380 and 390 may be implemented as transceivers configured to support wire-based or wireless signal communication. This communication may involve, for example, sending and receiving messages, parameters, and/or other types of information.

The UE 302, the base station 304, and the network entity 306 also include other components that may be used in conjunction with the operations as disclosed herein. The UE 302 includes processor circuitry implementing a processing system 332 for providing functionality relating to, for example, wireless positioning, and for providing other processing functionality. The base station 304 includes a processing system 384 for providing functionality relating to, for example, wireless positioning as disclosed herein, and for providing other processing functionality. The network entity 306 includes a processing system 394 for providing functionality relating to, for example, wireless positioning as disclosed herein, and for providing other processing functionality. The processing systems 332, 384, and 394 may therefore provide means for processing, such as means for determining, means for calculating, means for receiving, means for transmitting, means for indicating, etc. In an aspect, the processing systems 332, 384, and 394 may include, for example, one or more processors, such as one or more general purpose processors, multi-core processors, ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGA), other programmable logic devices or processing circuitry, or various combinations thereof.

The UE 302, the base station 304, and the network entity 306 include memory circuitry implementing memory components 340, 386, and 396 (e.g., each including a memory device), respectively, for maintaining information (e.g., information indicative of reserved resources, thresholds, parameters, and so on). The memory components 340, 386, and 396 may therefore provide means for storing, means for retrieving, means for maintaining, etc. In some cases, the UE 302, the base station 304, and the network entity 306 may include RFFP-P Modules 342, 388, and 398, respectively. The RFFP-P Modules 342, 388, and 398 may be hardware circuits that are part of or coupled to the processing systems 332, 384, and 394, respectively, that, when executed, cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. In other aspects, the RFFP-P Modules 342, 388, and 398 may be external to the processing systems 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the RFFP-P Modules 342, 388, and 398 may be memory modules stored in the memory components 340, 386, and 396, respectively, that, when executed by the processing systems 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. FIG. 3A illustrates possible locations of the RFFP-P Module 342, which may be part of the WWAN transceiver 310, the memory component 340, the processing system 332, or any combination thereof, or may be a standalone component. FIG. 3B illustrates possible locations of the RFFP-P Module 388, which may be part of the WWAN transceiver 350, the memory component 386, the processing system 384, or any combination thereof, or may be a standalone component. FIG. 3C illustrates possible locations of the RFFP-P Module 398, which may be part of the network interface(s) 390, the memory component 396, the processing system 394, or any combination thereof, or may be a standalone component.

The UE 302 may include one or more sensors 344 coupled to the processing system 332 to provide means for sensing or detecting movement and/or orientation information that is independent of motion data derived from signals received by the WWAN transceiver 310, the short-range wireless transceiver 320, and/or the SPS receiver 330. By way of example, the sensor(s) 344 may include an accelerometer (e.g., a micro-electrical mechanical systems (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric pressure altimeter), and/or any other type of movement detection sensor. Moreover, the sensor(s) 344 may include a plurality of different types of devices and combine their outputs in order to provide motion information. For example, the sensor(s) 344 may use a combination of a multi-axis accelerometer and orientation sensors to provide the ability to compute positions in 2D and/or 3D coordinate systems.

In addition, the UE 302 includes a user interface 346 providing means for providing indications (e.g., audible and/or visual indications) to a user and/or for receiving user input (e.g., upon user actuation of a sensing device such a keypad, a touch screen, a microphone, and so on). Although not shown, the base station 304 and the network entity 306 may also include user interfaces.

Referring to the processing system 384 in more detail, in the downlink, IP packets from the network entity 306 may be provided to the processing system 384. The processing system 384 may implement functionality for an RRC layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The processing system 384 may provide RRC layer functionality associated with broadcasting of system information (e.g., master information block (MIB), system information blocks (SIBs)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression/decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through automatic repeat request (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

The transmitter 354 and the receiver 352 may implement Layer-1 (L1) functionality associated with various signal processing functions. Layer-1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The transmitter 354 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM symbol stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with a respective spatial stream for transmission.

At the UE 302, the receiver 312 receives a signal through its respective antenna(s) 316. The receiver 312 recovers information modulated onto an RF carrier and provides the information to the processing system 332. The transmitter 314 and the receiver 312 implement Layer-1 functionality associated with various signal processing functions. The receiver 312 may perform spatial processing on the information to recover any spatial streams destined for the UE 302. If multiple spatial streams are destined for the UE 302, they may be combined by the receiver 312 into a single OFDM symbol stream. The receiver 312 then converts the OFDM symbol stream from the time-domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 304. These soft decisions may be based on channel estimates computed by a channel estimator. The soft decisions are then decoded and de-interleaved to recover the data and control signals that were originally transmitted by the base station 304 on the physical channel. The data and control signals are then provided to the processing system 332, which implements Layer-3 (L3) and Layer-2 (L2) functionality.

In the uplink, the processing system 332 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the core network. The processing system 332 is also responsible for error detection.

Similar to the functionality described in connection with the downlink transmission by the base station 304, the processing system 332 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

Channel estimates derived by the channel estimator from a reference signal or feedback transmitted by the base station 304 may be used by the transmitter 314 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the transmitter 314 may be provided to different antenna(s) 316. The transmitter 314 may modulate an RF carrier with a respective spatial stream for transmission.

The uplink transmission is processed at the base station 304 in a manner similar to that described in connection with the receiver function at the UE 302. The receiver 352 receives a signal through its respective antenna(s) 356. The receiver 352 recovers information modulated onto an RF carrier and provides the information to the processing system 384.

In the uplink, the processing system 384 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 302. IP packets from the processing system 384 may be provided to the core network. The processing system 384 is also responsible for error detection.

For convenience, the UE 302, the base station 304, and/or the network entity 306 are shown in FIGS. 3A to 3C as including various components that may be configured according to the various examples described herein. It will be appreciated, however, that the illustrated blocks may have different functionality in different designs.

The various components of the UE 302, the base station 304, and the network entity 306 may communicate with each other over data buses 334, 382, and 392, respectively. The components of FIGS. 3A to 3C may be implemented in various ways. In some implementations, the components of FIGS. 3A to 3C may be implemented in one or more circuits such as, for example, one or more processors and/or one or more ASICs (which may include one or more processors). Here, each circuit may use and/or incorporate at least one memory component for storing information or executable code used by the circuit to provide this functionality. For example, some or all of the functionality represented by blocks 310 to 346 may be implemented by processor and memory component(s) of the UE 302 (e.g., by execution of appropriate code and/or by appropriate configuration of processor components). Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by processor and memory component(s) of the base station 304 (e.g., by execution of appropriate code and/or by appropriate configuration of processor components). Also, some or all of the functionality represented by blocks 390 to 398 may be implemented by processor and memory component(s) of the network entity 306 (e.g., by execution of appropriate code and/or by appropriate configuration of processor components). For simplicity, various operations, acts, and/or functions are described herein as being performed “by a UE,” “by a base station,” “by a network entity,” etc. However, as will be appreciated, such operations, acts, and/or functions may actually be performed by specific components or combinations of components of the UE 302, base station 304, network entity 306, etc., such as the processing systems 332, 384, 394, the transceivers 310, 320, 350, and 360, the memory components 340, 386, and 396, the RFFP-P Modules 342, 388, and 398, etc.

In some designs, the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may be distinct from a network operator or operation of cellular network infrastructure. For example, the network entity 306 may be a component of a private network (e.g., which may be configured to communicate with UE 302 via the BS 304 or independently from the BS 304).

Various frame structures may be used to support downlink and uplink transmissions between network nodes (e.g., base stations and UEs). FIG. 4A is a diagram 400 illustrating an example of a downlink frame structure, according to aspects of the disclosure. FIG. 4B is a diagram 430 illustrating an example of channels within the downlink frame structure, according to aspects of the disclosure. FIG. 4C is a diagram 450 illustrating an example of an uplink frame structure, according to aspects of the disclosure. FIG. 4D is a diagram 480 illustrating an example of channels within an uplink frame structure, according to aspects of the disclosure. Other wireless communications technologies may have different frame structures and/or different channels.

LTE, and in some cases NR, utilizes OFDM on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. Unlike LTE, however, NR has an option to use OFDM on the uplink as well. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth. For example, the spacing of the subcarriers may be 15 kilohertz (kHz) and the minimum resource allocation (resource block) may be 12 subcarriers (or 180 kHz). Consequently, the nominal FFT size may be equal to 128, 256, 512, 1024, or 2048 for system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

LTE supports a single numerology (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR may support multiple numerologies (μ), for example, subcarrier spacings of 15 kHz (μ=0), 30 kHz (μ=1), 60 kHz (μ=2), 120 kHz (μ=3), and 240 kHz (μ=4) or greater may be available. In each subcarrier spacing, there are 14 symbols per slot. For 15 kHz SCS (μ=0), there is one slot per subframe, 10 slots per frame, the slot duration is 1 millisecond (ms), the symbol duration is 66.7 microseconds (μs), and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 50. For 30 kHz SCS (μ=1), there are two slots per subframe, 20 slots per frame, the slot duration is 0.5 ms, the symbol duration is 33.3 μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 100. For 60 kHz SCS (μ=2), there are four slots per subframe, 40 slots per frame, the slot duration is 0.25 ms, the symbol duration is 16.7 μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 200. For 120 kHz SCS (μ=3), there are eight slots per subframe, 80 slots per frame, the slot duration is 0.125 ms, the symbol duration is 8.33 μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 400. For 240 kHz SCS (μ=4), there are 16 slots per subframe, 160 slots per frame, the slot duration is 0.0625 ms, the symbol duration is 4.17 μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 800.

In the example of FIGS. 4A to 4D, a numerology of 15 kHz is used. Thus, in the time domain, a 10 ms frame is divided into 10 equally sized subframes of 1 ms each, and each subframe includes one time slot. In FIGS. 4A to 4D, time is represented horizontally (on the X axis) with time increasing from left to right, while frequency is represented vertically (on the Y axis) with frequency increasing (or decreasing) from bottom to top.

A resource grid may be used to represent time slots, each time slot including one or more time-concurrent resource blocks (RBs) (also referred to as physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into multiple resource elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. In the numerology of FIGS. 4A to 4D, for a normal cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and six consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

Some of the REs carry downlink reference (pilot) signals (DL-RS). The DL-RS may include PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, etc. FIG. 4A illustrates example locations of REs carrying PRS (labeled “R”).

A collection of resource elements (REs) that are used for transmission of PRS is referred to as a “PRS resource.” The collection of resource elements can span multiple PRBs in the frequency domain and ‘N’ (such as 1 or more) consecutive symbol(s) within a slot in the time domain. In a given OFDM symbol in the time domain, a PRS resource occupies consecutive PRBs in the frequency domain.

The transmission of a PRS resource within a given PRB has a particular comb size (also referred to as the “comb density”). A comb size ‘N’ represents the subcarrier spacing (or frequency/tone spacing) within each symbol of a PRS resource configuration. Specifically, for a comb size ‘N,’ PRS are transmitted in every Nth subcarrier of a symbol of a PRB. For example, for comb-4, for each symbol of the PRS resource configuration, REs corresponding to every fourth subcarrier (such as subcarriers 0, 4, 8) are used to transmit PRS of the PRS resource. Currently, comb sizes of comb-2, comb-4, comb-6, and comb-12 are supported for DL-PRS. FIG. 4A illustrates an example PRS resource configuration for comb-6 (which spans six symbols). That is, the locations of the shaded REs (labeled “R”) indicate a comb-6 PRS resource configuration.

Currently, a DL-PRS resource may span 2, 4, 6, or 12 consecutive symbols within a slot with a fully frequency-domain staggered pattern. A DL-PRS resource can be configured in any higher layer configured downlink or flexible (FL) symbol of a slot. There may be a constant energy per resource element (EPRE) for all REs of a given DL-PRS resource. The following are the frequency offsets from symbol to symbol for comb sizes 2, 4, 6, and 12 over 2, 4, 6, and 12 symbols. 2-symbol comb-2: {0, 1}; 4-symbol comb-2: {0, 1, 0, 1}; 6-symbol comb-2: {0, 1, 0, 1, 0, 1}; 12-symbol comb-2: {0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1}; 4-symbol comb-4: {0, 2, 1, 3}; 12-symbol comb-4: {0, 2, 1, 3, 0, 2, 1, 3, 0, 2, 1, 3}; 6-symbol comb-6: {0, 3, 1, 4, 2, 5}; 12-symbol comb-6: {0, 3, 1, 4, 2, 5, 0, 3, 1, 4, 2, 5}; and 12-symbol comb-12: {0, 6, 3, 9, 1, 7, 4, 10, 2, 8, 5, 11}.

A “PRS resource set” is a set of PRS resources used for the transmission of PRS signals, where each PRS resource has a PRS resource ID. In addition, the PRS resources in a PRS resource set are associated with the same TRP. A PRS resource set is identified by a PRS resource set ID and is associated with a particular TRP (identified by a TRP ID). In addition, the PRS resources in a PRS resource set have the same periodicity, a common muting pattern configuration, and the same repetition factor (such as “PRS-ResourceRepetitionFactor”) across slots. The periodicity is the time from the first repetition of the first PRS resource of a first PRS instance to the same first repetition of the same first PRS resource of the next PRS instance. The periodicity may have a length selected from 2∧μ*{4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, 10240} slots, with μ=0, 1, 2, 3. The repetition factor may have a length selected from {1, 2, 4, 6, 8, 16, 32} slots.

A PRS resource ID in a PRS resource set is associated with a single beam (or beam ID) transmitted from a single TRP (where a TRP may transmit one or more beams). That is, each PRS resource of a PRS resource set may be transmitted on a different beam, and as such, a “PRS resource,” or simply “resource,” also can be referred to as a “beam.” Note that this does not have any implications on whether the TRPs and the beams on which PRS are transmitted are known to the UE.

A “PRS instance” or “PRS occasion” is one instance of a periodically repeated time window (such as a group of one or more consecutive slots) where PRS are expected to be transmitted. A PRS occasion also may be referred to as a “PRS positioning occasion,” a “PRS positioning instance, a “positioning occasion,” “a positioning instance,” a “positioning repetition,” or simply an “occasion,” an “instance,” or a “repetition.”

A “positioning frequency layer” (also referred to simply as a “frequency layer”) is a collection of one or more PRS resource sets across one or more TRPs that have the same values for certain parameters. Specifically, the collection of PRS resource sets has the same subcarrier spacing and cyclic prefix (CP) type (meaning all numerologies supported for the PDSCH are also supported for PRS), the same Point A, the same value of the downlink PRS bandwidth, the same start PRB (and center frequency), and the same comb-size. The Point A parameter takes the value of the parameter “ARFCN-ValueNR” (where “ARFCN” stands for “absolute radio-frequency channel number”) and is an identifier/code that specifies a pair of physical radio channel used for transmission and reception. The downlink PRS bandwidth may have a granularity of four PRBs, with a minimum of 24 PRBs and a maximum of 272 PRBs. Currently, up to four frequency layers have been defined, and up to two PRS resource sets may be configured per TRP per frequency layer.

The concept of a frequency layer is somewhat like the concept of component carriers and bandwidth parts (BWPs), but different in that component carriers and BWPs are used by one base station (or a macro cell base station and a small cell base station) to transmit data channels, while frequency layers are used by several (usually three or more) base stations to transmit PRS. A UE may indicate the number of frequency layers it can support when it sends the network its positioning capabilities, such as during an LTE positioning protocol (LPP) session. For example, a UE may indicate whether it can support one or four positioning frequency layers.

FIG. 4B illustrates an example of various channels within a downlink slot of a radio frame. In NR, the channel bandwidth, or system bandwidth, is divided into multiple BWPs. A BWP is a contiguous set of PRBs selected from a contiguous subset of the common RBs for a given numerology on a given carrier. Generally, a maximum of four BWPs can be specified in the downlink and uplink. That is, a UE can be configured with up to four BWPs on the downlink, and up to four BWPs on the uplink. Only one BWP (uplink or downlink) may be active at a given time, meaning the UE may only receive or transmit over one BWP at a time. On the downlink, the bandwidth of each BWP should be equal to or greater than the bandwidth of the SSB, but it may or may not contain the SSB.

Referring to FIG. 4B, a primary synchronization signal (PSS) is used by a UE to determine subframe/symbol timing and a physical layer identity. A secondary synchronization signal (SSS) is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a PCI. Based on the PCI, the UE can determine the locations of the aforementioned DL-RS. The physical broadcast channel (PBCH), which carries an MIB, may be logically grouped with the PSS and SSS to form an SSB (also referred to as an SS/PBCH). The MIB provides a number of RBs in the downlink system bandwidth and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH, such as system information blocks (SIBs), and paging messages.

The physical downlink control channel (PDCCH) carries downlink control information (DCI) within one or more control channel elements (CCEs), each CCE including one or more RE group (REG) bundles (which may span multiple symbols in the time domain), each REG bundle including one or more REGs, each REG corresponding to 12 resource elements (one resource block) in the frequency domain and one OFDM symbol in the time domain. The set of physical resources used to carry the PDCCH/DCI is referred to in NR as the control resource set (CORESET). In NR, a PDCCH is confined to a single CORESET and is transmitted with its own DMRS. This enables UE-specific beamforming for the PDCCH.

In the example of FIG. 4B, there is one CORESET per BWP, and the CORESET spans three symbols (although it may be only one or two symbols) in the time domain. Unlike LTE control channels, which occupy the entire system bandwidth, in NR, PDCCH channels are localized to a specific region in the frequency domain (i.e., a CORESET). Thus, the frequency component of the PDCCH shown in FIG. 4B is illustrated as less than a single BWP in the frequency domain. Note that although the illustrated CORESET is contiguous in the frequency domain, it need not be. In addition, the CORESET may span less than three symbols in the time domain.

The DCI within the PDCCH carries information about uplink resource allocation (persistent and non-persistent) and descriptions about downlink data transmitted to the UE, referred to as uplink and downlink grants, respectively. More specifically, the DCI indicates the resources scheduled for the downlink data channel (e.g., PDSCH) and the uplink data channel (e.g., PUSCH). Multiple (e.g., up to eight) DCIs can be configured in the PDCCH, and these DCIs can have one of multiple formats. For example, there are different DCI formats for uplink scheduling, for downlink scheduling, for uplink transmit power control (TPC), etc. A PDCCH may be transported by 1, 2, 4, 8, or 16 CCEs in order to accommodate different DCI payload sizes or coding rates.

As illustrated in FIG. 4C, some of the REs (labeled “R”) carry DMRS for channel estimation at the receiver (e.g., a base station, another UE, etc.). A UE may additionally transmit SRS in, for example, the last symbol of a slot. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. In the example of FIG. 4C, the illustrated SRS is comb-2 over one symbol. The SRS may be used by a base station to obtain the channel state information (CSI) for each UE. CSI describes how an RF signal propagates from the UE to the base station and represents the combined effect of scattering, fading, and power decay with distance. The system uses the SRS for resource scheduling, link adaptation, massive MIMO, beam management, etc.

Currently, an SRS resource may span 1, 2, 4, 8, or 12 consecutive symbols within a slot with a comb size of comb-2, comb-4, or comb-8. The following are the frequency offsets from symbol to symbol for the SRS comb patterns that are currently supported. 1-symbol comb-2: {0}; 2-symbol comb-2: {0, 1}; 4-symbol comb-2: {0, 1, 0, 1}; 4-symbol comb-4: {0, 2, 1, 3}; 8-symbol comb-4: {0, 2, 1, 3, 0, 2, 1, 3}; 12-symbol comb-4: {0, 2, 1, 3, 0, 2, 1, 3, 0, 2, 1, 3}; 4-symbol comb-8: {0, 4, 2, 6}; 8-symbol comb-8: {0, 4, 2, 6, 1, 5, 3, 7}; and 12-symbol comb-8: {0, 4, 2, 6, 1, 5, 3, 7, 0, 4, 2, 6}.

A collection of resource elements that are used for transmission of SRS is referred to as an “SRS resource,” and may be identified by the parameter “SRS-ResourceId.” The collection of resource elements can span multiple PRBs in the frequency domain and N (e.g., one or more) consecutive symbol(s) within a slot in the time domain. In a given OFDM symbol, an SRS resource occupies consecutive PRBs. An “SRS resource set” is a set of SRS resources used for the transmission of SRS signals, and is identified by an SRS resource set ID (“SRS-ResourceSetId”).

Generally, a UE transmits SRS to enable the receiving base station (either the serving base station or a neighboring base station) to measure the channel quality between the UE and the base station. However, SRS can also be specifically configured as uplink positioning reference signals for uplink-based positioning procedures, such as uplink time difference of arrival (UL-TDOA), round-trip-time (RTT), uplink angle-of-arrival (UL-AoA), etc. As used herein, the term “SRS” may refer to SRS configured for channel quality measurements or SRS configured for positioning purposes. The former may be referred to herein as “SRS-for-communication” and/or the latter may be referred to as “SRS-for-positioning” when needed to distinguish the two types of SRS.

Several enhancements over the previous definition of SRS have been proposed for SRS-for-positioning (also referred to as “UL-PRS”), such as a new staggered pattern within an SRS resource (except for single-symbol/comb-2), a new comb type for SRS, new sequences for SRS, a higher number of SRS resource sets per component carrier, and a higher number of SRS resources per component carrier. In addition, the parameters “SpatialRelationInfo” and “PathLossReference” are to be configured based on a downlink reference signal or SSB from a neighboring TRP. Further still, one SRS resource may be transmitted outside the active BWP, and one SRS resource may span across multiple component carriers. Also, SRS may be configured in RRC connected state and only transmitted within an active BWP. Further, there may be no frequency hopping, no repetition factor, a single antenna port, and new lengths for SRS (e.g., 8 and 12 symbols). There also may be open-loop power control and not closed-loop power control, and comb-8 (i.e., an SRS transmitted every eighth subcarrier in the same symbol) may be used. Lastly, the UE may transmit through the same transmit beam from multiple SRS resources for UL-AoA. All of these are features that are additional to the current SRS framework, which is configured through RRC higher layer signaling (and potentially triggered or activated through MAC control element (CE) or DCI).

FIG. 4D illustrates an example of various channels within an uplink slot of a frame, according to aspects of the disclosure. A random-access channel (RACH), also referred to as a physical random-access channel (PRACH), may be within one or more slots within a frame based on the PRACH configuration. The PRACH may include six consecutive RB pairs within a slot. The PRACH allows the UE to perform initial system access and achieve uplink synchronization. A physical uplink control channel (PUCCH) may be located on edges of the uplink system bandwidth. The PUCCH carries uplink control information (UCI), such as scheduling requests, CSI reports, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and HARQ ACK/NACK feedback. The physical uplink shared channel (PUSCH) carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and/or UCI.

Note that the terms “positioning reference signal” and “PRS” generally refer to specific reference signals that are used for positioning in NR and LTE systems. However, as used herein, the terms “positioning reference signal” and “PRS” may also refer to any type of reference signal that can be used for positioning, such as but not limited to, PRS as defined in LTE and NR, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc. In addition, the terms “positioning reference signal” and “PRS” may refer to downlink or uplink positioning reference signals, unless otherwise indicated by the context. If needed to further distinguish the type of PRS, a downlink positioning reference signal may be referred to as a “DL-PRS,” and an uplink positioning reference signal (e.g., an SRS-for-positioning, PTRS) may be referred to as an “UL-PRS.” In addition, for signals that may be transmitted in both the uplink and downlink (e.g., DMRS, PTRS), the signals may be prepended with “UL” or “DL” to distinguish the direction. For example, “UL-DMRS” may be differentiated from “DL-DMRS.”

Machine learning may be used to generate models that may be used to facilitate various aspects associated with positioning, including processing of reference signals for positioning (RS-Ps), such as feature extraction, reporting of RS-P measurements (e.g., picking which extracted features to report, and so on.

Machine learning models are generally categorized as either supervised or unsupervised. A supervised model may further be sub-categorized as either a regression or classification model. Supervised learning involves learning a function that maps an input to an output based on example input-output pairs. For example, assume a training dataset with two variables of age (input) and height (output). A supervised learning model could be generated so as to predict the height of a person based on their age. In regression models, the output is continuous. One example of a regression model is linear regression. The idea of linear regression is simply finding a line that best fits the data. Extensions of linear regression include multiple linear regression (e.g., finding a plane of best fit) and polynomial regression (e.g., finding a curve of best fit).

Another example of a machine learning model is a decision tree model. In a decision tree model, a tree structure is defined with a plurality of nodes. Decisions are used to move from a root node at a top of the decision tree to a leaf node at the bottom of the decision tree (i.e., a node with no further child nodes). Generally, a higher number of nodes in the decision tree model is correlated with higher decision accuracy.

Another example of a machine learning model is a decision forest. Random forests are an ensemble learning technique that builds off of decision trees. Random forests involve creating multiple decision trees using bootstrapped datasets of the original data and randomly selecting a subset of variables at each step of the decision tree. The model then selects the mode of all of the predictions of each decision tree. By relying on a “majority wins” model, the risk of error from an individual tree is reduced.

Another example of a machine learning model is a neural network (NN). An NN is essentially a network of mathematical equations. NNs accept one or more input variables, and by going through a network of equations, results in one or more output variables. To put another way, a neural network takes in a vector of inputs and returns a vector of outputs.

FIG. 5 illustrates an NN 500 in accordance with an aspect of the disclosure. The NN 500 includes an input layer that provide Inputs 1 . . . n, “Hidden” layers h₁. . . h_(n) for processing the Inputs 1 . . . n, and an output layer that provides Outputs 1 . . . n. The value of n need not be the same between the respective layers (e.g., the number of Inputs, Hidden layers, and Outputs can be the same or different). In some designs, the Hidden layers may include linear function(s) and/or activation function(s) that the nodes each successive Hidden layer process from the previous Hidden layer.

In classification models, the output is discrete. One example of a classification model is logistic regression. Logistic regression is similar to linear regression, but is used to model the probability of a finite number of outcomes, typically two. In essence, a logistic equation is created in such a way that the output values can only be between 0 and 1. Another example of a classification model is a support vector machine. For example, assume there are two classes of data. A support vector machine will find a hyperplane or a boundary between the two classes of data that maximizes the margin between the two classes. There are many planes that can separate the two classes, but only one plane can maximize the margin or distance between the classes. Another example of a classification model is Näive Bayes, which is based on Bayes Theorem. Other examples of classification models include decision tree, random forest, and NN, similar to the examples described above except that the output is discrete rather than continuous.

Unlike supervised learning, unsupervised learning is used to draw inferences and find patterns from input data without references to labeled outcomes. Two examples of unsupervised learning models include clustering and dimensionality reduction.

Clustering is an unsupervised technique that involves the grouping, or clustering, of data points. Clustering is frequently used for customer segmentation, fraud detection, and document classification. Common clustering techniques include k-means clustering, hierarchical clustering, mean shift clustering, and density-based clustering. Dimensionality reduction is the process of reducing the number of random variables under consideration by obtaining a set of principal variables. In simpler terms, dimensionality reduction is the process of reducing the dimension of a feature set (in even simpler terms, reducing the number of features). Most dimensionality reduction techniques can be categorized as either feature elimination or feature extraction. One example of dimensionality reduction is called principal component analysis (PCA). In the simplest sense, PCA involves project higher dimensional data (e.g., 3 dimensions) to a smaller space (e.g., 2 dimensions). This results in a lower dimension of data (e.g., 2 dimensions instead of 3 dimensions) while keeping all original variables in the model.

Irrespective of which machine learning model is used, at a high-level a machine learning module (e.g., implemented via a respective processing system such as processing system 332 or 384 or 394) of a component (e.g., UE 302, BS 304, network entity 306, etc.) may be configured to iteratively analyze training input data (e.g., measurements of RS-Ps to/from various target UEs) and to associate this training input data with an output data set (e.g., a set of possible or likely candidate locations of the various target UEs), thereby enabling later determination of the same output data set when presented with similar input data (e.g., from other target UEs at the same or similar location).

One particular positioning technique is RF fingerprinting for positioning (RFFP-P). In RFFP-P, knowledge of channel measurements (or a channel frequency response (CFR) or channel impulse response or reference signal received power (RSRP) or reference signal strength indicator (RSSI)) along with a ground truth location (e.g., ascertained via a high-precision positioning scheme, such as a gantry XYZ positioning system, an automatic guided vehicle (AGV) positioning system, survey based system, refined position information obtained from classical positioning techniques, etc.) may be determined for several locations in a region of interest (ROI). Then, when a new channel measurement is obtained from a UE inside the ROI, the new channel measurement can be used to predict the UE location. For example, UL-SRS-P from the UE may be measured at TRP(s) to determine the CFR or channel impulse response. RFFP-P implicitly leverages spatial filtering and interpolation, and can be more accurate than other positioning techniques in certain environments (e.g., if a limited number of gNBs is available and/or if a limited number of LOS links to the gNBs is available). In some designs, the ground truth location may correspond to a high precision localization done by the UE (e.g., carrier phase or multi-constellation or multi-frequency GNSS).

FIG. 6 illustrates an example of RFFP-P model process 600 in accordance with an aspect of the disclosure. A network component 602 (e.g., location server, LMF, etc.) collects measurement data (e.g., CFRs) associated with UL-SRS-Ps as measured by TRPs and which are transmitted by UEs at known locations inside of ROI 604. Various locations inside the ROI 604 are denoted as X in FIG. 6. As a CFR (e.g., at one or more of the TRPs) is determined for a particular location X, that CFR becomes part of the RFFP-P model. For example, a UE transmit location (x,y,z) may be associated with a particular CFR for TRP_(j), and so on. At 608, the RFFP-P model may be sent to a database 610. At 612, the database 610 may in turn transmit the RFFP-P model to a NN RF mapping unit 614. Next, a UE is located at a location X denoted as 616 inside of the ROI 604, but the UE location is not yet known. At 618, CFR(s) of UL-SRS-P is measured at one or more TRP(s) and sent to the NN RF mapping unit 614. At 620, the NN RF mapping unit 614 then uses the RFFP-P model to predict the UE location. Assuming the RFFP-P model is accurate and the CFR(s) at 618 are measured with good quality, the prediction position should correspond to the location X denoted as 616 inside of the ROI 604.

In some systems (e.g., NR systems), training of RFFP-P models using machine learning (e.g., using NNs) may be performed on the network side (rather than at the UEs) because the network will typically have access to more data. For example, the network can aggregate data from various UEs over a long period of time. Some networks have dedicated infrastructure for training models, and can propagate the learned models to future UEs which later connect to the network. The network can also refine the model from UEs which joined later than the training phase. Some models may be used at the network to help the network make decisions. Some models may be transmitted to the UE and the inference happens at the UE. For example, consider the case of training a network which predicts the position of UEs. In some designs, it is efficient to train at the network using SRS transmissions from the UE. However, in some designs, the trained model may then only be implemented with respect to other SRS transmissions measured at the network, and is not used for RFFP-P implemented at the UE-side.

FIG. 7 is a diagram 700 illustrating a base station (BS) 702 (which may correspond to any of the base stations described herein) in communication with a UE 704 (which may correspond to any of the UEs described herein). Referring to FIG. 7, the base station 702 may transmit a beamformed signal to the UE 704 on one or more transmit beams 702 a, 702 b, 702 c, 702 d, 702 e, 702 f, 702 g, 702 h, each having a beam identifier that can be used by the UE 704 to identify the respective beam. Where the base station 702 is beamforming towards the UE 704 with a single array of antennas (e.g., a single TRP/cell), the base station 702 may perform a “beam sweep” by transmitting first beam 702 a, then beam 702 b, and so on until lastly transmitting beam 702 h. Alternatively, the base station 702 may transmit beams 702 a-702 h in some pattern, such as beam 702 a, then beam 702 h, then beam 702 b, then beam 702 g, and so on. Where the base station 702 is beamforming towards the UE 704 using multiple arrays of antennas (e.g., multiple TRPs/cells), each antenna array may perform a beam sweep of a subset of the beams 702 a-702 h. Alternatively, each of beams 702 a-702 h may correspond to a single antenna or antenna array. In FIG. 7, an LOS path is depicted at 710.

FIG. 7 further illustrates the paths 712 c, 712 d, 712 e, 712 f, and 712 g followed by the beamformed signal transmitted on beams 702 c, 702 d, 702 e, 702 f, and 702 g, respectively. Each path 712 c, 712 d, 712 e, 712 f, 712 g may correspond to a single “multipath” or, due to the propagation characteristics of radio frequency (RF) signals through the environment, may be comprised of a plurality (a cluster) of “multipaths.” Note that although only the paths for beams 702 c-702 g are shown, this is for simplicity, and the signal transmitted on each of beams 702 a-702 h will follow some path. In the example shown, the paths 712 c, 712 d, 712 e, and 712 f are straight lines, while path 712 g reflects off an obstacle 720 (e.g., a building, vehicle, terrain feature, etc.).

The UE 704 may receive the beamformed signal from the base station 702 on one or more receive beams 704 a, 704 b, 704 c, 704 d. Note that for simplicity, the beams illustrated in FIG. 7 represent either transmit beams or receive beams, depending on which of the base station 702 and the UE 704 is transmitting and which is receiving. Thus, the UE 704 may also transmit a beamformed signal to the base station 702 on one or more of the beams 704 a-704 d, and the base station 702 may receive the beamformed signal from the UE 704 on one or more of the beams 702 a-702 h.

In an aspect, the base station 702 and the UE 704 may perform beam training to align the transmit and receive beams of the base station 702 and the UE 704. For example, depending on environmental conditions and other factors, the base station 702 and the UE 704 may determine that the best transmit and receive beams are 702 d and 704 b, respectively, or beams 702 e and 704 c, respectively. The direction of the best transmit beam for the base station 702 may or may not be the same as the direction of the best receive beam, and likewise, the direction of the best receive beam for the UE 704 may or may not be the same as the direction of the best transmit beam.

As will be appreciated from FIGS. 5-7, uplink signals (e.g., SRS) used to train an RFFP-P model may be reciprocal with respect to corresponding downlink beam(s) of one or more wireless nodes (e.g., gNBs, TRPs, reference UE with a known location, etc.). Link reciprocity may be associated with common channel response characteristics in both directions (e.g., UL and DL). Aspects of the disclosure are thereby directed to training a measurement model (e.g., an RFFP-P model) based at least in part upon measurement information (e.g., CFR) of a set of uplink signals (e.g., SRS) from one or more UEs, and then implementing the measurement (e.g., RFFP-P) model with respect to processing of signal(s) (e.g., PRS(s)) at a target UE where the signal(s) (e.g., PRS(s)) are transported over one or more downlink beams that is reciprocal to the uplink signal(s) used to train the measurement (e.g., RFFP-P) model. Such aspects may leverage the benefit of network-based training of the measurement (e.g., RFFP-P) model in combination with UE application of the measurement (e.g., RFFP-P) model. Such aspects may provide various technical advantages, such as improved UE signal processing. In a more specific example, such aspects may provide various technical advantages for a positioning application such as improved positioning accuracy, particularly in scenarios where other positioning techniques work poorly (e.g., if a limited number of gNBs is available and/or if a limited number of LOS links to the gNBs is available).

FIG. 8 illustrates an exemplary process 800 of wireless communication, according to aspects of the disclosure. In an aspect, the process 800 may be performed by a network component, such as a BS or gNB such as BS 304, or a network entity 306 (e.g., core network component such as LMF, a location server, or a component of a private network separate from a serving network of a target UE, etc.).

Referring to FIG. 8, at 810, the network component (e.g., network interface(s) 380 or 390, receiver 352 or 362, etc.) obtains measurement information associated with a set of uplink signals from one or more UEs, wherein the set of uplink signals has reciprocity with one or more downlink beams of one or more wireless nodes. For example, the measurement information may be measured by one or more TRPs or reference UEs over a period of time. In some designs, the measurement information may include CFRs and the set of uplink signals may include SRS (e.g., UL-SRS-P).

Referring to FIG. 8, at 820, the network component (e.g., processing system 332 or 384 or 394, RFFP-P module 342 or 388 or 398, etc.) determines a measurement model (e.g., an RFFP-P model) based on the measurement information associated with the set of uplink signals from the one or more UEs. In some designs, the measurement model (e.g., an RFFP-P model) is generated as part of 820, while in other designs, the measurement model (e.g., an RFFP-P model) is refined from a previous version of the measurement model (e.g., an RFFP-P model) at 820. An example implementation of 820 corresponds to the process 600 of FIG. 6. On example implementation of the measurement model (e.g., an RFFP-P model) itself corresponds to an NN, such as the NN 500 of FIG. 5.

Referring to FIG. 8, at 830, the network component (e.g., network interface(s) 380 or 390, transmitter 354 or 364, etc.) provides, to a target UE, the measurement model (e.g., an RFFP-P model) for processing of at least one signal (e.g., PRS) associated with the one or more downlink beams of the one or more wireless nodes. The target UE may be the same or different from the UE(s) from which the uplink signal(s) are transmitted in association with the collection of the measurement information (e.g., the UEs used to train the measurement model may not necessarily be the same as the UEs that later apply the measurement model).

FIG. 9 illustrates an exemplary process 900 of wireless communication, according to aspects of the disclosure. In an aspect, the process 900 may be performed by a target UE, such as UE 302.

Referring to FIG. 9, at 910, the target UE (e.g., receiver 312 or 322, etc.) receives, from a network component (e.g., a BS or gNB such as BS 304, or a network entity 306 such as a core network component or a component of a private network separate from a serving network of a target UE, etc.), a measurement model (e.g., an RFFP-P model) that is trained based upon measurement information associated with a set of uplink signals from one or more UEs, the set of uplink signals having reciprocity with one or more downlink beams of one or more wireless nodes. For example, the measurement information may be measured by one or more TRPs or reference UEs over a period of time. In some designs, the measurement information may include CFRs and the set of uplink signals may include SRS (e.g., UL-SRS-P).

Referring to FIG. 9, at 920, the target UE (e.g., receiver 312 or 322, etc.) receives, on the one or more downlink beams from the one or more wireless nodes, at least one signal (e.g., PRS).

Referring to FIG. 9, at 930, the target UE (e.g., processing system 332, RFFP-P model 342, etc.) processes the at least one signal (e.g., PRS) based at least in part on the measurement model (e.g., RFFP-P model). For example, the processing of the at least one signal (e.g., PRS) may include determining a CFR associated with the at least one signal (e.g., PRS), comparing the determined CFR with a set of CFRs associated with a set of candidate locations inside of a ROI (e.g., via NN processing), and predicting a location of the target UE as one of the candidate locations among the set of candidate locations based on the CFR comparison.

Referring to FIGS. 8-9, in some designs, the measurement model may correspond to an RFFP-P model and the at least one signal that is processed based on the RFFP-P model may correspond to at least one PRS. However, aspects of the disclosure may also be applicable to non-RFFP-P positioning and/or to non-positioning implementations as well. In other words, various signal types and applications may take advantage of reciprocity-based application of measurement models. Below, examples are provided primarily with a positioning context, but it will be appreciated that such examples are non-limiting and aspects may be applicable to various signal processing applications.

Referring to FIGS. 8-9, in some designs, the one or more wireless nodes include a TRP of a base station or a reference UE. In some designs, the set of uplink signals includes one or more SRS. However, SRS is not a requirement and other UL signals or data may be used to derive measurement information that can be factored into the RFFP-P model generation or refinement. In some designs, the one or more UEs for which measurement information is collected for training of the measurement model (e.g., RFFP-P model) may be network-selected.

Referring to FIGS. 8-9, in some designs, the determination of the measurement model (e.g., RFFP-P model) at 820 includes providing the measurement information as training data into a machine learning algorithm to generate or refine the measurement model (e.g., RFFP-P model) (e.g., as described above with respect to FIGS. 5-6). In some designs, the measurement model (e.g., RFFP-P model) is implemented as one or more NNs. For example, the measurement model (e.g., RFFP-P model) may accept CFR(s) of measured signal(s) (e.g., PRS(s)) as input data, may then process the input data based on CFR(s) associated with a set of candidate locations in an ROI, and provide an output of a predicted location of the target UE.

Referring to FIGS. 8-9, in some designs, the measurement model (e.g., RFFP-P model) is refined based on measurement information associated with the at least one signal (e.g., PRS) from the target UE, measurement information associated with one or more other signals (e.g., PRSs) from the target UE or one or more other target UEs, or a combination thereof. The refinement may occur locally at the respective UE(s), or alternatively may occur at the network component (e.g., PRS measurement data is fed back to the network component, which then refines the RFFP-P model).

Referring to FIGS. 8-9, in some designs, the measurement model (e.g., RFFP-P model) is tailored to one or more UE types, a target bandwidth (BW), a number of base stations associated with a respective measurement (e.g., positioning or PRS) procedure, a number of antennas or panels associated with a respective measurement (e.g., positioning or PRS) procedure, or a combination thereof. Hence, even in scenarios involving the same beam(s) and TRP(s), different measurement models (e.g., RFFP-P models) may be generated and applied based on secondary criteria. For example, the network may transmit (e.g., broadcast or unicast) UE-specific models depending on UE operating conditions. As an example, some UEs may desire a model that works on 20 MHz (e.g., RedCap UEs), others on 100 MHz BW, etc. There may be UE-specific customizations, including operating BWP, number of gNBs or antennas or panels associated with a positioning session, etc. In some designs, the network component can train all these models using a common training framework and may reuse some or all of the training data across measurement models (e.g., different measurement models can be generated using combinations of the same training data).

Referring to FIGS. 8-9, in some designs, the measurement model (e.g., RFFP-P model) may be used for position estimation, or “inference”, at the UE. Here, it is assumed that the DL-PRS used for the RFFP-P model-based inference maintains reciprocity with the respective uplink signals that were used to train the particular RFFP-P model. In some designs, the target UE may optionally refine the RFFP-P model or modify the input data to account for UE-specific characteristics, such as RF delays. In some designs, the network may optionally provide location assistance data to help the UE refine the RFFP-P model and/or the input data (e.g., the input data into the NN of the RFFP-P model), such as Tx and/or Rx group delay information associated with one or more TRPs at the network, etc.

FIG. 10 illustrates an example implementation 1000 of the processes 800-900 of FIGS. 8-9 in accordance with an aspect of the disclosure. UEs 302_1, 302_2 and 303_3 transmit UL-SRS-Ps 1002, 1004 and 1006, respectively, to one or more TRPs of BS 304. BS 304 measures CFRs associated with each of UL-SRS-Ps 1002, 1004 and 1006, respectively, and transmits the measured CFRs to the network component at 1008. In an example where the network component corresponds to BS 304 itself, the transmission at 1008 corresponds to an internal transfer of data between logical components of BS 304 (e.g., over a respective data bus 382, etc.). The network component may then use the reported CFRs to generate or refine the RFFP-P model.

FIG. 11 illustrates an example implementation 1100 of the processes 800-900 of FIGS. 8-9 in accordance with another aspect of the disclosure. At 1102, the network component transmits a current version of the RFFP-P model to BS 304, which in turn transmits (e.g., via separate transmissions) the RFFP-P model and PRS(s) to UE 302_4 at 1104. For example, the RFFP-P model may be indicated to UE 302_4 via location assistance data. In some designs, PRSs may be transmitted over certain panels, beams, TRPs, etc. which are associated with the RFFP-P model (e.g., the RFFP-P model is chosen from a group of RFFP-P models). As noted above, secondary criteria may also be considered in context with RFFP-P selection, such as UE type (e.g., RedCap UE, etc.) and so on.

FIG. 12 illustrates an example implementation 1200 of the processes 800-900 of FIGS. 8-9 in accordance with another aspect of the disclosure. At 1202, the network component transmits a current version of the RFFP-P model to BS 304, which in turn transmits (e.g., via separate transmissions) the RFFP-P model and PRS(s) to UEs 302_1, 302_2 and 302_3 at 1204, 1206 and 1208, respectively. As will be appreciated, different RFFP-P models may be transmitted to the UEs 302_1, 302_2 and 302_3 depending on TRP, beam(s) over which the PRS(s) are to be transmitted, and so on. UEs 302_1, 302_2 and 302_3 optionally provide PRS feedback information (e.g., CFR measurement data) at 1210, 1212 and 12143, respectively, which is then optionally forwarded to the network component at 1216. The network component can then further refine the RFFP-P model(s) based on DL-PRS measurement data in addition to UL-SRS-P measurement data. Again, such aspects may be implemented specifically where beam (or link) reciprocity is present between the DL-PRS(s) and the respective UL-SRS-P(s).

In FIG. 12, a joint learning (or federated learning) approach is implemented, whereby an initial version of the RFFP-P model is trained by UL-SRS, and the UE (or network component) refines the model based on the local data and the DL PRS. The UE transmits the local model to the network and the model is pooled at the network component using federated learning concepts. This way, the network is jointly trained at the data from the gNB and the UE. At the end of training, in some designs, both the network and the UEs can use the same model for inference.

In the detailed description above it can be seen that different features are grouped together in examples. This manner of disclosure should not be understood as an intention that the example clauses have more features than are explicitly mentioned in each clause. Rather, the various aspects of the disclosure may include fewer than all features of an individual example clause disclosed. Therefore, the following clauses should hereby be deemed to be incorporated in the description, wherein each clause by itself can stand as a separate example. Although each dependent clause can refer in the clauses to a specific combination with one of the other clauses, the aspect(s) of that dependent clause are not limited to the specific combination. It will be appreciated that other example clauses can also include a combination of the dependent clause aspect(s) with the subject matter of any other dependent clause or independent clause or a combination of any feature with other dependent and independent clauses. The various aspects disclosed herein expressly include these combinations, unless it is explicitly expressed or can be readily inferred that a specific combination is not intended (e.g., contradictory aspects, such as defining an element as both an insulator and a conductor). Furthermore, it is also intended that aspects of a clause can be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

Implementation examples are described in the following numbered clauses:

Clause 1. A method of operating a network component, comprising: obtaining measurement information associated with a set of uplink signals from one or more user equipments (UEs), wherein the set of uplink signals has reciprocity with one or more downlink beams of one or more wireless nodes; determining a measurement model based on the measurement information associated with the set of uplink signals from the one or more UEs; and providing, to a target UE, the measurement model for processing of at least one signal associated with the one or more downlink beams of the one or more wireless nodes.

Clause 2. The method of clause 1, wherein the measurement model corresponds to a radio frequency fingerprinting for positioning (RFFP-P) model, and wherein the at least one signal comprises at least one positioning reference signal (PRS).

Clause 3. The method of any of clauses 1 to 2, wherein the one or more wireless nodes include a transmission reception point (TRP) of a base station or a reference UE.

Clause 4. The method of any of clauses 1 to 3, wherein the set of uplink signals comprises one or more sounding reference signals (SRSs).

Clause 5. The method of any of clauses 1 to 4, wherein the determination comprises providing the measurement information as training data into a machine learning algorithm to generate or refine the measurement model.

Clause 6. The method of clause 5, wherein the model is implemented as one or more neural networks.

Clause 7. The method of any of clauses 1 to 6, wherein the measurement model is refined based on measurement information from the target UE that is associated with the at least one signal, measurement information from the target UE or one or more other target UEs that is associated with one or more other signals, or a combination thereof.

Clause 8. The method of any of clauses 1 to 7, wherein the measurement model is tailored to one or more UE types, a target bandwidth (BW), a number of base stations associated with a respective positioning procedure, a number of antennas or panels associated with a respective positioning procedure, or a combination thereof.

Clause 9. The method of any of clauses 1 to 8, wherein the at least one signal comprises one or more downlink signals, one or more sidelink signals, or a combination thereof.

Clause 10. The method of any of clauses 1 to 9, wherein the measurement model is jointly generated or refined based on a combination of the measurement information associated with the set of uplink signals from the one or more UEs and measurement feedback from the target UE related to the at least one signal.

Clause 11. A method of operating a target user equipment (UE), comprising: receiving, from a network component, a measurement model that is trained based upon measurement information associated with a set of uplink signals from one or more UEs, the set of uplink signals having reciprocity with one or more downlink beams of one or more wireless nodes; receiving, on the one or more downlink beams from the one or more wireless nodes, at least one signal; and processing the at least one signal based at least in part on the measurement model.

Clause 12. The method of clause 11, wherein the measurement model corresponds to a radio frequency fingerprinting for positioning (RFFP-P) model, and wherein the at least one signal comprises at least one positioning reference signal (PRS).

Clause 13. The method of any of clauses 11 to 12, wherein the one or more wireless nodes include a transmission reception point (TRP) of a base station or a reference UE.

Clause 14. The method of any of clauses 11 to 13, wherein the set of uplink signals comprises one or more sounding reference signals (SRSs).

Clause 15. The method of any of clauses 11 to 14, wherein the measurement model is generated or refined by providing the measurement information as training data into a machine learning algorithm.

Clause 16. The method of clause 15, wherein the measurement model is implemented as one or more neural networks.

Clause 17. The method of any of clauses 11 to 16, further comprising: transmitting measurement information associated with the at least one signal to the network component.

Clause 18. The method of clause 17, further comprising: receiving a modified version of the measurement model that is refined based on the transmitted measurement information.

Clause 19. The method of any of clauses 11 to 18, further comprising: refining the measurement model based on information specific to the target UE, network-provided location assistance data, or a combination thereof.

Clause 20. The method of any of clauses 11 to 19, wherein the measurement model is tailored to one or more UE types, a target bandwidth (BW), a number of base stations associated with a respective positioning procedure, a number of antennas or panels associated with a respective positioning procedure, or a combination thereof.

Clause 21. The method of any of clauses 11 to 20, wherein the at least one signal comprises one or more downlink signals, one or more sidelink signals, or a combination thereof.

Clause 22. The method of any of clauses 11 to 21, wherein the processing comprises: determining a channel frequency response (CFR) associated with the at least one PRS; comparing the determined CFR with a set of CFRs associated with a set of candidate locations inside of a region of interest (ROI); and predicting a location of the target UE as one of the candidate locations among the set of candidate locations based on the CFR comparison.

Clause 23. An apparatus comprising a memory and at least one processor communicatively coupled to the memory, the memory and the at least one processor configured to perform a method according to any of clauses 1 to 22.

Clause 24. An apparatus comprising means for performing a method according to any of clauses 1 to 22.

Clause 25. A non-transitory computer-readable medium storing computer-executable instructions, the computer-executable comprising at least one instruction for causing a computer or processor to perform a method according to any of clauses 1 to 22.

Those of skill in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

Further, those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an ASIC, a field-programable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The methods, sequences and/or algorithms described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An example storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

In one or more example aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

While the foregoing disclosure shows illustrative aspects of the disclosure, it should be noted that various changes and modifications could be made herein without departing from the scope of the disclosure as defined by the appended claims. The functions, steps and/or actions of the method claims in accordance with the aspects of the disclosure described herein need not be performed in any particular order. Furthermore, although elements of the disclosure may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. 

What is claimed is:
 1. A method of operating a network component, comprising: obtaining measurement information associated with a set of uplink signals from one or more user equipments (UEs), wherein the set of uplink signals has reciprocity with one or more downlink beams of one or more wireless nodes; determining a measurement model based on the measurement information associated with the set of uplink signals from the one or more UEs; and providing, to a target UE, the measurement model for processing of at least one signal associated with the one or more downlink beams of the one or more wireless nodes.
 2. The method of claim 1, wherein the measurement model corresponds to a radio frequency fingerprinting for positioning (RFFP-P) model, and wherein the at least one signal comprises at least one positioning reference signal (PRS).
 3. The method of claim 1, wherein the one or more wireless nodes include a transmission reception point (TRP) of a base station or a reference UE.
 4. The method of claim 1, wherein the set of uplink signals comprises one or more sounding reference signals (SRSs).
 5. The method of claim 1, wherein the determination comprises providing the measurement information as training data into a machine learning algorithm to generate or refine the measurement model.
 6. The method of claim 5, wherein the model is implemented as one or more neural networks.
 7. The method of claim 1, wherein the measurement model is refined based on measurement information from the target UE that is associated with the at least one signal, measurement information from the target UE or one or more other target UEs that is associated with one or more other signals, or a combination thereof.
 8. The method of claim 1, wherein the measurement model is tailored to one or more UE types, a target bandwidth (BW), a number of base stations associated with a respective positioning procedure, a number of antennas or panels associated with a respective positioning procedure, or a combination thereof.
 9. The method of claim 1, wherein the at least one signal comprises one or more downlink signals, one or more sidelink signals, or a combination thereof.
 10. The method of claim 1, wherein the measurement model is jointly generated or refined based on a combination of the measurement information associated with the set of uplink signals from the one or more UEs and measurement feedback from the target UE related to the at least one signal.
 11. A method of operating a target user equipment (UE), comprising: receiving, from a network component, a measurement model that is trained based upon measurement information associated with a set of uplink signals from one or more UEs, the set of uplink signals having reciprocity with one or more downlink beams of one or more wireless nodes; receiving, on the one or more downlink beams from the one or more wireless nodes, at least one signal; and processing the at least one signal based at least in part on the measurement model.
 12. The method of claim 11, wherein the measurement model corresponds to a radio frequency fingerprinting for positioning (RFFP-P) model, and wherein the at least one signal comprises at least one positioning reference signal (PRS).
 13. The method of claim 11, wherein the one or more wireless nodes include a transmission reception point (TRP) of a base station or a reference UE.
 14. The method of claim 11, wherein the set of uplink signals comprises one or more sounding reference signals (SRSs).
 15. The method of claim 11, wherein the measurement model is generated or refined by providing the measurement information as training data into a machine learning algorithm.
 16. The method of claim 15, wherein the measurement model is implemented as one or more neural networks.
 17. The method of claim 11, further comprising: transmitting measurement information associated with the at least one signal to the network component.
 18. The method of claim 17, further comprising: receiving a modified version of the measurement model that is refined based on the transmitted measurement information.
 19. The method of claim 11, further comprising: refining the measurement model based on information specific to the target UE, network-provided location assistance data, or a combination thereof.
 20. The method of claim 11, wherein the measurement model is tailored to one or more UE types, a target bandwidth (BW), a number of base stations associated with a respective positioning procedure, a number of antennas or panels associated with a respective positioning procedure, or a combination thereof.
 21. The method of claim 11, wherein the at least one signal comprises one or more downlink signals, one or more sidelink signals, or a combination thereof.
 22. The method of claim 11, wherein the processing comprises: determining a channel frequency response (CFR) associated with the at least one PRS; comparing the determined CFR with a set of CFRs associated with a set of candidate locations inside of a region of interest (ROI); and predicting a location of the target UE as one of the candidate locations among the set of candidate locations based on the CFR comparison.
 23. A network component, comprising: a memory; a communication interface; and at least one processor communicatively coupled to the memory and the communication interface, the at least one processor configured to: obtain measurement information associated with a set of uplink signals from one or more user equipments (UEs), wherein the set of uplink signals has reciprocity with one or more downlink beams of one or more wireless nodes; determine a measurement model based on the measurement information associated with the set of uplink signals from the one or more UEs; and provide, to a target UE via the communication interface, the measurement model for processing of at least one signal associated with the one or more downlink beams of the one or more wireless nodes.
 24. The network component of claim 23, wherein the measurement model corresponds to a radio frequency fingerprinting for positioning (RFFP-P) model, and wherein the at least one signal comprises at least one positioning reference signal (PRS).
 25. The network component of claim 23, wherein the one or more wireless nodes include a transmission reception point (TRP) of a base station or a reference UE.
 26. The network component of claim 23, wherein the set of uplink signals comprises one or more sounding reference signals (SRSs).
 27. A target user equipment (UE), comprising: a memory; a communication interface; and at least one processor communicatively coupled to the memory and the communication interface, the at least one processor configured to: receive, via the communication interface, from a network component, a measurement model that is trained based upon measurement information associated with a set of uplink signals from one or more UEs, the set of uplink signals having reciprocity with one or more downlink beams of one or more wireless nodes; receive, via the communication interface, on the one or more downlink beams from the one or more wireless nodes, at least one signal; and process the at least one signal based at least in part on the measurement model.
 28. The target UE of claim 27, wherein the measurement model corresponds to a radio frequency fingerprinting for positioning (RFFP-P) model, and wherein the at least one signal comprises at least one positioning reference signal (PRS).
 29. The target UE of claim 27, wherein the one or more wireless nodes include a transmission reception point (TRP) of a base station or a reference UE.
 30. The target UE of claim 27, wherein the set of uplink signals comprises one or more sounding reference signals (SRSs). 